This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
- When I put in an action group and add changeDocumentMode, the document stays in edit mode after the save.
- When I add a script block to the action group, it won't build because a script block can't be put in an action group.
- If I take out the action group, so it's just saveDocument, and put a "normal" print in the Agent to load an URL, it doesn't work
- However, if I take the print out of the Agent and stick context.redirectToHome() in the postDocumentSave() it works like a charm.
- So it appears Agents can't interact with the browser at all with XPages. The XPage has to fully save the document, then pass its noteID as a parameter document, and the Agent can't output anything directly to the web page like it used to, not even a redirect. It's possible one could output JSON on an asynchronous call, I haven't tried that, but the decade-long web model of Agent use appears to be thoroughly dead.
- I'm not saying that's bad ... or good. I'm simply saying that's how it is, so someone else has the opportunity to say "no it's not", or "that's right". Nothing more...
Feedback response number DGIE7Z6K4B created by ~Holly Zekhipisonnivu on 12/28/2009
Sadly this doesn't work...
Return to top
. . . . Sadly this doesn't work... (~James Brewever... 28.Dec.09) 
